|
The Concurrent Versions System (CVS), also known as the Concurrent Versioning System, is a client-server free software revision control system in the field of software development. A version control system keeps track of all work and all changes in a set of files, and allows several developers (potentially widely separated in space and time) to collaborate. Dick Grune developed CVS as a series of shell scripts in July 1986.〔(【引用サイトリンク】title=CVS--Concurrent Versions System v1.12.12.1: Overview )〕 In addition to commercial software developers, CVS became popular with the open source software world and was released under the GNU General Public License. While there was regular development to add features and fix bugs in the past,〔(【引用サイトリンク】title=CVS Change Log )〕 including regular builds and test results,〔(【引用サイトリンク】title=CVS Test Results )〕 there have been no new releases since 2008.〔 The product is mature: new releases are not produced until there are requests for new features〔(【引用サイトリンク】title=Open requests for fixes/features )〕 or bug reports.〔(【引用サイトリンク】title=Requests for fixes/features )〕 == Features == CVS uses a client–server architecture: a server stores the current version(s) of a project and its history, and clients connect to the server in order to "check out" a complete copy of the project, work on this copy and then later "check in" their changes. Typically, the client and server connect over a LAN or over the Internet, but client and server may both run on the same machine if CVS has the task of keeping track of the version history of a project with only local developers. The server software normally runs on Unix (although at least the CVSNT server also supports various flavours of Microsoft Windows), while CVS clients may run on any major operating-system platform. Several developers may work on the same project concurrently, each one editing files within their own "working copy" of the project, and sending (or ''checking in'') their modifications to the server. To avoid the possibility of people stepping on each other's toes, the server only accepts changes made to the most recent version of a file. Developers are therefore expected to keep their working copy up-to-date by incorporating other people's changes on a regular basis. This task is mostly handled automatically by the CVS client, requiring manual intervention only when an edit conflict arises between a checked-in modification and the yet-unchecked local version of a file. If the check in operation succeeds, then the version numbers of all files involved automatically increment, and the CVS-server writes a user-supplied description line, the date and the author's name to its log files. CVS can also run external, user-specified log processing scripts following each commit. These scripts are installed by an entry in CVS's loginfo file, which can trigger email notification or convert the log data into a Web-based format. Clients can also compare versions, request a complete history of changes, or check out a historical snapshot of the project as of a given date or as of a revision number. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Concurrent Versions System」の詳細全文を読む スポンサード リンク
|